home *** CD-ROM | disk | FTP | other *** search
- Path: news.iadfw.net!usenet
- From: Larry Weiss <lfw@iadfw.net>
- Newsgroups: comp.lang.c
- Subject: Re: malloc question
- Date: Sun, 10 Mar 1996 18:42:23 -0600
- Organization: ...
- Message-ID: <314376EF.C10@iadfw.net>
- References: <4htonk$350@news.hklink.net> <4huctt$arv@sparcserver.lrz-muenchen.de> <4hv5qpINNp8a@keats.ugrad.cs.ubc.ca>
- NNTP-Posting-Host: dal03-27.ppp.iadfw.net
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 2.0 (Win16; I)
-
- Kazimir Kylheku wrote:
- >
- > ... malloc() is no mere external
- > function, it is a special language feature painstakingly dressed up to look
- > like a library function, even to the point that you can take the address of
- > malloc() and call it via a function pointer.
- > --
-
-
- As I've said before, the fundamental definition of the very nature of
- standard library "functions" is the most profound impact of the
- C Language Standardization project.
-